The important thing to remember when gathering evidence is that the more evidence the better - that is, the more evidence you gather to demonstrate your skills, the more confident an assessor can be that you have learned the skills not just at one point in time, but are continuing to apply and develop those skills (as opposed to just learning for the test!). Furthermore, one piece of evidence that you collect will not usualy demonstrate all the required criteria for a unit of competency, whereas multiple overlapping pieces of evidence will usually do the trick!
From the Wiki University
What evidence can you provide to prove your understanding of each of the following citeria?
Prepare the test
|
|
Establish and document, the testing framework and schedule Completed |
Evidence:
|
Determine the processes and functions to be tested, and assign the quantitative and qualitative performance benchmarks to each process and function Completed |
Evidence:
|
Benchmark and document the page templates, style guides and expected traffic loads Completed |
Evidence:
|
Determine and document the test methodology Completed |
Evidence:
|
Assemble and brief, the testing panel on the conduct of the test Completed |
Evidence:
|
Develop user and installation manuals, according to the target audience’s understanding and needs Completed |
Evidence:
|
Test individual pages
|
|
Test the pages, against style guides and templates Completed |
Evidence:
|
Test the pages, for consistency in structure and content Completed |
Evidence:
|
Apply the automatic testing software Completed |
Evidence:
|
Document page gross statistics of confirmed results of tests Completed |
Evidence:
|
Test page relationships against the business requirements
|
|
Test the installation, and the examples listed in instruction manual Completed |
Evidence:
|
Test page navigability using a variety of browsers Completed |
Evidence:
|
Test the ease of use and functionality against the requirements Completed |
Evidence:
|
Test software interface points, against the business and technical requirements Completed |
Evidence:
|
Test site security and privacy against the business requirements Completed |
Evidence:
|
Test the response time against the business requirements Completed |
Evidence:
|
Conduct load simulation testing, using single and multiple independent browsers, or automated load testing tools Completed |
Evidence:
|
Apply and document further tests
|
|
4.1 Test the website's ability to handle concurrent access Completed |
Evidence:
|
Test conformance to the applicable privacy, accessibility, and acceptable usage policy standards Completed |
Evidence:
|
Apply the automatic testing software Completed |
Evidence:
|
Collect, collate and document the results from the sample user, and data from the automated test Completed |
Evidence:
|
Evaluate the test results
|
|
Consolidate and compare the results to the benchmarks Completed |
Evidence:
|
Identify results that fail to meet the benchmarks, and conduct a site remedial iteration Completed |
Evidence:
|
Record and document the test results as the site performance baseline, against which further development or updating can be measured Completed |
Evidence:
|
Provide evaluation feedback to the appropriate person Completed |
Evidence:
|
Ensure that the appropriate person signs off on the site, prior to the ‘go live’ date Completed |
Evidence:
|